sdtaylor/jornadadroneanalysis

jornadadroneanalysis's Issues

To Do

• drop unused analysis scripts
• make simulation/drone folders
• save all figs with distinct sizes
• drop fixed sized ROI's? I never really used them. maybe port that code to another repo
• [ ]

equations

VI_{Pixel} = Cover_{veg}\times VI_{veg} + (1-Cover_{veg})\times VI_{soil} + \varepsilon 

roi notes

NORT roi example

IBP roi example

P9 roi example

manuscript to do for 1st submission

• organize code into simulation/drone/other folder
• archive all unused but potentially usefull scripts
• redo nort pixel classification with just nort data
• organize references
• drop P9 and IBP from all the scripts
• drop unused stuff in vi_simulation_tools.R, put '.' on helper functions
• prep zenodo submission. Everything can go in the git repo too except NORT NDVI images (if they're included)
• repo readme

Analysis stuff

• re-run simulation analysis with extended EOS possibility, shouldn't change anything overall. but I had to do this with the NORT drone phenology since EOS was bounded at 365.
• check on missing 2019-09-26 date from NORT data
• redo sos uncertainty figure

paper logistics

• switch to latex
• cite zenodo in data statement
• quick proof read/spell check in overleaf
• ORISE affilication

revision todo

1st revision

writing

• redo figures, "curvature" -> "change rate"
• deal with 30-40% thing in abstract

manuscript logistics

• cover letter/rebuttal
• track changes manuscript
• zip of all original figures
• zip of latex files
• new zenodo version (can do this after acceptance)

signed forms from everyone http://downloads.spj.sciencemag.org/remotesensing/License_to_Publish_for_Remote.pdf

• shawn
• dawn
• feng
• ruben