{"action":"opened","issue":{"url":"https://api.github.com/repos/terraref/reference-data/issues/18","labels_url":"https://api.github.com/repos/terraref/reference-data/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/terraref/reference-data/issues/18/comments","events_url":"https://api.github.com/repos/terraref/reference-data/issues/18/events","html_url":"https://github.com/terraref/reference-data/issues/18","id":111883136,"number":18,"title":"Define set of traits / phenotypes that will be used in GWAS and yield prediction  ","user":{"login":"dlebauer","id":464871,"avatar_url":"https://avatars.githubusercontent.com/u/464871?v=3","gravatar_id":"","url":"https://api.github.com/users/dlebauer","html_url":"https://github.com/dlebauer","followers_url":"https://api.github.com/users/dlebauer/followers","following_url":"https://api.github.com/users/dlebauer/following{/other_user}","gists_url":"https://api.github.com/users/dlebauer/gists{/gist_id}","starred_url":"https://api.github.com/users/dlebauer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dlebauer/subscriptions","organizations_url":"https://api.github.com/users/dlebauer/orgs","repos_url":"https://api.github.com/users/dlebauer/repos","events_url":"https://api.github.com/users/dlebauer/events{/privacy}","received_events_url":"https://api.github.com/users/dlebauer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/terraref/reference-data/labels/ICASA","name":"ICASA","color":"fbca04"},{"url":"https://api.github.com/repos/terraref/reference-data/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":{"login":"chporter","id":320153,"avatar_url":"https://avatars.githubusercontent.com/u/320153?v=3","gravatar_id":"","url":"https://api.github.com/users/chporter","html_url":"https://github.com/chporter","followers_url":"https://api.github.com/users/chporter/followers","following_url":"https://api.github.com/users/chporter/following{/other_user}","gists_url":"https://api.github.com/users/chporter/gists{/gist_id}","starred_url":"https://api.github.com/users/chporter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chporter/subscriptions","organizations_url":"https://api.github.com/users/chporter/orgs","repos_url":"https://api.github.com/users/chporter/repos","events_url":"https://api.github.com/users/chporter/events{/privacy}","received_events_url":"https://api.github.com/users/chporter/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/terraref/reference-data/milestones/14","html_url":"https://github.com/terraref/reference-data/milestones/5.1%20Define%20validation%20&%20calibration%20data%20sets","labels_url":"https://api.github.com/repos/terraref/reference-data/milestones/14/labels","id":1340677,"number":14,"title":"5.1 Define validation & calibration data sets","description":"","creator":{"login":"rachelshekar","id":11740606,"avatar_url":"https://avatars.githubusercontent.com/u/11740606?v=3","gravatar_id":"","url":"https://api.github.com/users/rachelshekar","html_url":"https://github.com/rachelshekar","followers_url":"https://api.github.com/users/rachelshekar/followers","following_url":"https://api.github.com/users/rachelshekar/following{/other_user}","gists_url":"https://api.github.com/users/rachelshekar/gists{/gist_id}","starred_url":"https://api.github.com/users/rachelshekar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rachelshekar/subscriptions","organizations_url":"https://api.github.com/users/rachelshekar/orgs","repos_url":"https://api.github.com/users/rachelshekar/repos","events_url":"https://api.github.com/users/rachelshekar/events{/privacy}","received_events_url":"https://api.github.com/users/rachelshekar/received_events","type":"User","site_admin":false},"open_issues":1,"closed_issues":0,"state":"open","created_at":"2015-10-06T16:24:35Z","updated_at":"2015-10-16T18:17:31Z","due_on":"2015-12-11T06:00:00Z","closed_at":null},"comments":0,"created_at":"2015-10-16T18:17:31Z","updated_at":"2015-10-16T18:17:31Z","closed_at":null,"body":"* Define traits that will be used in GWAS study, including variable names, units, and methods of measurement / validation.\r\n\r\nfor example:\r\n\r\n| name |  units | description | method of measurement |\r\n| -----|----|----|----|----|\r\n| SLA   | m2 kg-1   | Specific leaf area leaf area per unit mass | hole punch  |\r\n\r\nUltimately, these should be entered into the trait database which will look like this: https://www.betydb.org/variables/15. \r\n\r\n* [ ] what is the core set of traits that teams are interested in measuring for calibrating algorithms to derive traits from sensors, predict yields and crop fitness, and use in genomic analysis? (@JeffWhiteAZ)\r\n   * a few easy ones include specific leaf area, height, leaf area index, leaf number\r\n   * what other simple sensor-derived values, such as mean greenness by plot or plant, NDVI, and other indices\r\n* [ ] Is there a set of trait names, canonical units, and definitions (similar to [CF Standard Names](http://cfconventions.org/Data/cf-standard-names/29/build/cf-standard-name-table.html) that we can use for these  (@chporter)\r\n* [ ] How can we distinguish among sensor-derived and field (e.g. calibration / validation) measurements?\r\n  * BETYdb allows each trait record to be linked to a method defined in a separate table\r\n         this method of measurement, e.g. using a hole-punch vs. whole-leaf measurement of a leaf mass / area could affect the magnitude of the measurement, but at the plant scale is interpreted as the same trait. With calibrating precise sub-leaf measurements, we can subset data by method of measurement without distinguishing the variable names.\r\n  * in addition, when different models are used to estimate a parameter, and the parameter is only relevant for a specific model formulation (e.g. Ball-Berry, Leuning, and Medlyn variants of stomatal slope used to estimate leaf-level gas exchange), we use different records in the variables table, because the values are clearly defined as distinct."}}