Open oharac opened 5 years ago
@erinwinslow @molwilson @jacobgellman @oharac Hi there Team Lumpsucker! Thank you for organizing this Casey and this lovely creature that you selected to represent us :) Let's start coding!
Hey Team Lumpsucker! I've put in a few bits of code, and pushed to Github. Make sure to pull every time before you start working, to get any changes anyone else has made, and then to push frequently to make sure everyone else can get your modifications.
Hey squad! I was thinking I might start playing with the ch1 problems because I know I'm gonna be a bit all over the place the next few weeks (and bc Casey has done such a good job w the chapter code). I started a new .rmd, feel free to add/modify any answers... if you'd rather keep everything in one .rmd with the chapter code that is fine too!
Is it helpful to everyone else for me to take a crack at the code? I don't want to dissuade others from giving it a shot, and I know there are other approaches that might be better (e.g. I'll definitely take a look at JC's code 'cause we all know he's a certified badass). I figured people could hide my code chunks (and other people's) to try their own approach, then unhide the chunks to see how other people did it (to compare, or if they get stuck).
Good thought to do the questions on a separate .Rmd - good luck with 'em!
Personally I think its super helpful! And keeps me from getting stuck on one component.... thank you Casey for all your work/organizing!
Casey! Agreed with Molly, all your stuff is super helpful :)
I've been so busy I have barely looked at this, I am a terrible team member right now I'm sorry!
On Thu, Jul 11, 2019 at 7:28 PM Molly Wilson notifications@github.com wrote:
Personally I think its super helpful! And keeps me from getting stuck on one component.... thank you Casey for all your work/organizing!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eco-detectives/primer_of_ecology_r/issues/2?email_source=notifications&email_token=AH3K4FJZJ4H5GXBVBLDLEC3P7AJAVA5CNFSM4H4VCDQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZYW66Y#issuecomment-510750587, or mute the thread https://github.com/notifications/unsubscribe-auth/AH3K4FJ4H5AKRKGZEFNPP2DP7AJAVANCNFSM4H4VCDQA .
--
Erin M. Winslow Moorea Coral Reef LTER - PhD Student Bren School of Environmental Science & Management University of California, Santa Barbara erinmwinslow.com
MESM 2017
winslow@ucsb.edu ewinslow@bren.ucsb.edu ewinslow@bren.ucsb.edu ewinslow@bren.ucsb.edu Tel. 858.414.6371
hey team Lumpsucker! I saw Molly added some code and comments into our answer document ch1probs_lumpsucker.Rmd
, and I added a little as well. Everyone get in there and put in your thoughts and ideas, even if they're basically the same as what Molly and I put. Hope to hear from you all on Thursday!
@oharac, I added some code to my q1 but now can't knit the full markdown (stops after 2.1.4). Any thoughts on what I'm doing wrong...?
I had the same problem, it's because there are fancy tabs at the beginning of the document you can click!
Ahhh wow too fancy for me I guess! Thank you!
@erinwinslow @molwilson @jacobgellman @MireiaValle @oharac
Hey Team Lumpsucker! Most of us are remote so we'll probably have to rely on Github issues for communicating and coordinating. The early stuff is pretty basic, and then by section 1.6 gets more serious. Maybe we each copy a code chunk, use a comment to tag it with our name, and code it how we like; that way, if more than one person wants to try we'd just have two different versions of the chunk. Something like, for the first chunk: